Skip to content

Fix content type might not be in headers#89

Merged
maingoh merged 3 commits intomasterfrom
fix-content-type-response
Mar 30, 2020
Merged

Fix content type might not be in headers#89
maingoh merged 3 commits intomasterfrom
fix-content-type-response

Conversation

@maingoh
Copy link
Copy Markdown
Contributor

@maingoh maingoh commented Mar 30, 2020

It raised a KeyError if content-type was not in the headers and wasn't returning the response content

@maingoh maingoh requested a review from ibreschi March 30, 2020 13:15
@sonarqubecloud
Copy link
Copy Markdown

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@maingoh maingoh merged commit f479724 into master Mar 30, 2020
@maingoh maingoh deleted the fix-content-type-response branch March 30, 2020 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants